Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Even after changing the SELinux policy back to permissive mode (#885), quite a lot of integration tests on multihost mode were still failing. This PR contains multiple commits tackling these issues:
Use different file name for ctrl config
concatenate stderr and stdout in sshclient
The client for the podman container seems to concatenate stderr and stdout in its output parameter. In the SSH client stderr and stdout are different return variables. In order to not break the
exec_run
API of the Client class and still get a uniform behavior of both clients, lets concat stderr and stdout in the SSH client.actively check if bluechi_machine_lib exists
In order to avoid failing mkdir calls on subsequent tests for the bluechi_machine_lib, an active check is being made. If it doesn't exist yet, we create the directory and the library files. These files are not tracked and thus not deleted after a test. This way, we only create the lib once.
switch order of restoring created and changed files
When creating files, we first keep track of them in the list for newly created ones. If a file is already in that list and another file with the same path (dir+name) is created we keep create a backup and track it.
For clean-up we need to reverse that order - first restore tracked backup files and then remove created files. This ensures that there are no dangling files.
Example run with test failures:
http://artifacts.osci.redhat.com/testing-farm/c028903c-1611-4a93-be04-686594d8a210/
Example run after fixes:
http://artifacts.osci.redhat.com/testing-farm/754765a9-2181-462a-b4e3-688adf697743/
The flaky propagate test failed, unfortunately. This will be tackled in Integration Test for proxy service propagation is flaky #874)